Steam 9-in-1 machine (OTEMiniSteamNineInOne) incorrectly routed item output through mOutputBusses (always empty for steam machines), and always ran at 256 parallel regardless of the GUI setting.

Root Causes

• Output bus mismatch: Four overridden methods (addOutput, getStoredOutputs, getItemOutputSlots, getVoidOutputSlots) all iterated mOutputBusses. MTESteamMultiBase.addToMachineList() registers MTEHatchSteamBusOutput into mSteamOutputs, not mOutputBusses — making all item output attempts fail against an empty list.

• Parallel supplier bypassed GUI: createProcessingLogic() bound to this::getMaxParallelRecipes (hardcoded 256) instead of this::getTrueParallel, which respects powerPanelMaxParallel.

• Missing abstract method: getThemeTier() from MTESteamMultiBase was not implemented.

Changes

• Remove the four old-API output overrides. MTESteamMultiBase.getOutputBusses() already returns mSteamOutputs correctly; the modern ItemEjectionHelper path picks it up automatically.

• Fix parallel supplier:

  // Before
  }.setMaxParallelSupplier(this::getMaxParallelRecipes);
  // After
  }.setMaxParallelSupplier(this::getTrueParallel);

• Add getThemeTier() returning 2 (HP/steel, consistent with getTierRecipes() = 2).

• Remove imports that were only used by the deleted methods (filterValidMTEs, IInventory, IItemLockable, MTEHatchOutput, MTEHatchOutputBus, MTEHatchVoidBus, MTEHatchOutputBusME, ArrayList).

• Fixes Steam 9-in-1 machine problem #202

🔒 GitHub Advanced Security automatically protects Copilot coding agent pull requests. You can protect all pull requests by enabling Advanced Security for your repositories. Learn more about Advanced Security.